Automation interface

ABSTRACT

A system for controlling automation includes a machine which collects data generated by performance of an operation by the machine. A user device displays a machine control interface (MCI) corresponding to the machine. The MCI displays the collected data to a touch interface of the user device, and defines at least one touch activated user interface element (UIE) for manipulating the data. The user device can be enabled as an automation human machine interface (HMI) device for controlling an operation performed by the machine, such that a touch action applied to a UIE of the MCI controls the operation. A prerequisite condition to enabling the user device as an automation HMI device can include activation of an enabling switch selectively connected to the user device. The MCI can be stored in a memory of the enabling switch and retrieved from the enabling switch by the user device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application claims the benefit of U.S. application Ser. No.16/825,954 filed Mar. 20, 2020, U.S. Application Ser. No. 15/306,954filed Oct. 26, 2016 and issued as U.S. Pat. No. 10,599,133 on Mar. 24,2020, PCT Application PCT/US2015/029907 filed May 8, 2015, U.S.application Ser. No. 14/705,421 filed May 6, 2015 and issued as U.S.Pat. No. 10,048,670 on Aug. 14, 2018, U.S. Provisional Application61/990,148 filed May 8, 2014, U.S. Provisional Application 61/990,151filed May 8, 2014, U.S. Provisional Application 61/990,156 filed May 8,2014, U.S. Provisional Application 61/990,158 filed May 8, 2014, U.S.Provisional Application 61/990,159 filed May 8, 2014, U.S. ProvisionalApplication 61/990,163 filed May 8, 2014, U.S. Provisional Application61/990,169 filed May 8, 2014, U.S. Provisional Application 61/990,170filed May 8, 2014, and U.S. Provisional Application 61/990,172 filed May8, 2014, which are each hereby incorporated by reference in theirentirety.

TECHNICAL FIELD

The present disclosure relates generally to operating and managingautomated equipment, including collecting and capturing automation datausing an automation controller in communication with a computing device.

BACKGROUND

A facility may include multiple machines. Each machine can be controlledby a programmable logic controller (PLC) or similar controller connectedto multiple machine elements, power sources and sensors of the machine,to operate the machine in an automated mode. The controller incommunication with the sensors receives sensor inputs to the controllerindicating condition states of the various elements. The controller maybe programmed to scan at a predetermined frequency through a scan cycle,defined for example, by a sequence of operations (SOP) to be performedby the elements of the machine, and, based on the sensor inputs andcondition states received by the controller, selectively energize thepower sources to actuate the elements to perform operations defined bythe program. Each machine and its associated controller may be operatedindependently from each other machine. A snapshot of machine operatingdata, including timing data, collected at a historical point in time,may be displayed for monitoring on a user interface, for example,connected to the machine controller. The machine can be controlled bythe machine controller in one of an automated mode and a manual mode,where operator input to the machine controls are typically inputted byan operator to a control panel which is physically attached to themachine or the machine controller to restrict the location of theoperator when the machine is in operation.

SUMMARY

An automation operating and management system is provided whichconsolidates and analyzes inputs from multiple machines within anautomated enterprise, and displays inputs received from the multiplemachines using a user interface of a user device. In one example, theuser interface can include a touch screen of a portable user devicedisplaying a machine control interface including one or more graphicalcontrol elements. The machine control interface can be a machine controlinterface for a specific station, a specific element, a specificmachine, a group of elements, a group of stations, a group of machinesand/or a zone including multiple elements, stations and/or machines,etc. The graphical control elements are arranged relative to the machinecontrol interface such that a user can intuitively access data displayedfor the machine operation and/or control a machine operation byactivation and/or manipulation of one or more of the graphical controlelements defined by the machine control interface displayed on the touchscreen.

In one example, a system for controlling automation is provided whichincludes a machine in communication with a network. The machine collectsdata generated by performance of at least one operation by the machineand transmits the collected data to a network. A user device is incommunication with the network to receive a machine control interface(MCI) corresponding to the machine, where the user device includes atouch interface for display of the MCI. The MCI displays the collecteddata to the touch interface, and defines at least one touch activateduser interface element (UIE) for manipulating the data displayed by theMCI.

The operation performed by the machine can be one of a sequence ofoperations (SOP) performed by the machine such that the data collectedcan include at least one of a baseline cycle time for the operation andan actual cycle time for performance of the operation. In one example,the MCI displays the sequence of operations including the at least oneoperation, and further displays at least one of a baseline cycleindicator displaying the baseline cycle time of the at least oneoperation and an actual cycle indicator displaying the actual cycle timeof the at least one operation. The MCI can display the baseline cycleindicator and/or the actual cycle indicator in one of an SOP timelinedisplay and a machine heartbeat display. In one example, at least oneUIE defined by the MCI is defined by one of the operations displayed inthe sequence of operations. In another example, at least one UIE isdefined by the at least one of the baseline cycle indicator and theactual cycle indicator. The collected data can be viewed and/ormanipulated, and additional information can be displayed by the MCI, bya touch input to the UIE by a user of the user device.

In one example, the user device can be enabled as an automation humanmachine interface (HMI) device for controlling at least one operationperformed by the machine, such that a touch action applied to at leastone UIE defined by the MCI controls the operation. The automation HMIdevice can include an enabling switch connected to the user device whereactivation of the enabling switch is a prerequisite condition toenabling the user device as an automation HMI device. The MCI can bestored in a memory of the enabling switch such that the MCI is retrievedfrom the enabling switch by the user device. In an illustrative example,at least one UIE is defined by one of the baseline cycle indicator andthe actual cycle indicator, such that a touch action applied to the UIEas a sliding pressure in a first direction actuates performance of theoperation to a conclusion or end condition of the operation, and suchthat a touch action applied to the UIE as a sliding pressure in a seconddirection opposing the first direction actuates performance of theoperation to a start of the operation. In one example, the enablingswitch includes a trigger and a connector for connecting the enablingswitch to a user device, such that the user device is enabled as anautomation human machine interface (HMI) device for controlling the atleast one operation when the enabling switch is connected to the userdevice and the trigger is manually activated by a user.

In one example, an enabled area is defined by the location of themachine, and the automation HMI device is enabled to control the machinewhen the automation HMI device is located within the enabled area. Theautomation HMI device is disabled from controlling the machine when theautomation HMI device is located outside the enabled area. The enablingswitch can include a location device for determining a location of theenabling switch relative to the enabled area. The system can includeanother location device for use in determining the enabled area, andsuch that the location device of the enabling switch can selectivelycommunicate with the other location device to determine the location ofthe automation HMI device relative to the enabled area. In one example,the location devices are each radio frequency identification (RFID)devices. In another example, the location device included in theenabling switch is a global positioning system (GPS) device.

The machine can be selectively operated in an operating mode which isone of an automated mode and a manual mode. In one example, theautomation HMI device is enabled to control the machine when the machineis operated in the manual mode, and is disabled from controlling themachine when the machine is operated in the automatic mode. Theautomation HMI device can be in communication with the machine todetermine the operating mode of the machine.

The above features and advantages, and other features and advantages, ofthe present teachings are readily apparent from the following detaileddescription of some of the best modes and other embodiments for carryingout the present teachings, as defined in the appended claims, when takenin connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of an example of an automation operating andmanagement system including first, second, third and fourth levelcontrollers;

FIG. 2 is a schematic view of an example of a machine including a firstlevel controller and a second level controller;

FIG. 3 is a schematic illustration of an example of a machine sequenceof operations of a machine of the system of FIG. 1 ;

FIG. 4 is a schematic illustration of an example of a machine heartbeatof the sequence of operations of FIG. 3 ;

FIG. 5 is a schematic illustration of an example of a machine controlinterface showing the machine sequence of operations of FIG. 3 displayedon a user device;

FIG. 6 is a schematic illustration of an example of a machine controlinterface showing the machine heartbeat of FIG. 4 displayed on a userdevice;

FIG. 7 is a schematic illustration of an example of a machine controlinterface of FIG. 5 ;

FIG. 8 is a schematic illustration of an example of a machine controlinterface of FIG. 6 ;

FIG. 9 is a schematic illustration of an example of a user device ofFIG. 1 including an enabling switch;

FIG. 10 is a schematic of a facility management system of the system ofFIG. 1 , showing a plurality of machines each having an enabled area;

FIG. 11 is a schematic of a facility management system of the system ofFIG. 10 ; and

FIG. 12 is a schematic illustration of an example of the user device andenabling switch of FIG. 9 including a machine control interface.

DETAILED DESCRIPTION

Referring to the drawings wherein like reference numbers represent likecomponents throughout the several figures, the elements shown in FIGS.1-13 are not to scale or proportion. Accordingly, the particulardimensions and applications provided in the drawings presented hereinare not to be considered limiting. FIG. 1 shows an automation operatingand management system 10 for controlling systems, machines, and elementsoperating within an enterprise 12. The automation operating andmanagement system 10 may be referred to herein as an automationoperating system (AOS). The enterprise 12 includes an enterprise serverL4, which may also be referred to herein as a fourth layer server, forreceiving and consolidating data from multiple facilities 14 (shown inthe example of FIG. 1 as facilities 14A . . . 14 x and referred toherein collectively as facilities 14) within the enterprise 12. Each ofthe facilities 14 includes a facility server L3, which may also bereferred to herein as a third layer server, for receiving andconsolidating data from multiple facility systems SY (shown in theexample of FIG. 1 as systems SY1 . . . SYm and referred to hereincollectively as systems SY) within each of the facilities 14. Eachfacility server L3 is in communication with the enterprise server L4. Atleast one of the facility systems SY in each of the facilities 14 (shownin the example of facility 14A as system SY1) includes multiple machines16 (shown in the example of FIG. 1 as machines 16A . . . 16 y andreferred to herein collectively as machines 16). The machines 16 can beany machines that perform coordinated operations including automatedmachines. In an illustrative and non-limiting example described hereinthe machines 16 can be machines such as automated machines performingoperations in a manufacturing plant and/or an assembly facility. Theenterprise server L4 can be embodied as one or more computer deviceshaving a processor 94 and a memory 92, some of which iscomputer-readable tangible, non-transitory memory arranged on a printedcircuit board or otherwise available to the processor 94. Instructionsembodying the methods described herein may be programmed into memory 92and executed as needed via the processor 94 to provide functionality ofthe AOS 10 as described herein. The memory 92 may include, by way ofexample, sufficient read only memory (ROM), optical memory, flash orother solid state memory, and the like. Transitory memory such as randomaccess memory (RAM) and electrically-erasable programmable read-onlymemory (EEPROM) may also be included, along with other requiredcircuitry (not shown), including but not limited to a high-speed clock,current/voltage/temperature/speed/position sensing circuitry,analog-to-digital (A/D) circuitry, digital-to-analog (D/A) circuitry, adigital signal processor, and any necessary input/output (I/O) devicesand other signal conditioning and/or buffer circuitry. The enterpriseserver L4 can include a communications interface 96 for communicationwith other controllers and/or servers in the enterprise 12, includingfor example, for communication with each of a third layer server L3, asecond layer controller L2 and a first layer controller L1 of theenterprise 12. The fourth layer (enterprise) server L4, third layerservers L3, second layer controllers L2 and first layer controllers L1can be in communication with each other via a network 80, which may be awired or wireless network.

AOS 10 can include a data storage memory 90 which can be used to storedata received from one or more of the fourth layer server L4, thirdlayer servers L3, second layer controllers L2 and first layercontrollers L1. By way of example, the data storage memory 90 may beaccessed via the network 80 and/or may be external to the enterprise 12,for external data storage. The data storage memory 90 can be accessiblevia the enterprise server L4 and/or via the network 80. The data storagememory 90 can include, by way of example, sufficient read only memory(ROM), optical memory, flash or other solid state memory, and the liketo store data received from the enterprise 12. Transitory memory such asrandom access memory (RAM) and electrically-erasable programmableread-only memory (EEPROM) may also be included, along with otherrequired circuitry (not shown), including but not limited to ahigh-speed clock, analog-to-digital (A/D) circuitry, digital-to-analog(D/A) circuitry, a digital signal processor, and any necessaryinput/output (I/O) devices and other signal conditioning and/or buffercircuitry.

AOS 10 can further include one or more user devices (shown in theexample of FIG. 1 as user devices U1 . . . Uw and referred to hereincollectively as user devices U) in communication with the enterprise 12,via a wired connection or a wireless connection, for example, via thenetwork 80. By way of non-limiting example, a user device U can be acomputing device such as a personal computer, tablet, laptop, smartphone, personal digital assistant, or other personal computing devicefor viewing information including data related to and/or provided by theenterprise 12. In one example, the user device U can display a machinecontrol interface for one or more of the machines 16. The user device Ucan include a user interface such as a touch screen for interacting withthe information and data of the enterprise 12 and/or for controlling themachine 16 via the machine control interface.

In the example shown, each of the machines 16 includes a second layercontroller L2 and one or more first layer controllers L1. Each of themachine controllers L2 (shown in the example of FIG. 1 as machinecontrollers L2A . . . L2 y and referred to herein collectively asmachine controllers L2) within a respective facility 14 are incommunication with the respective facility controller L3 for thatfacility 14. A second layer controller L2 may also be referred to hereinas a machine controller. Each machine controller L2 of a respectivemachine 16 is in communication with the first layer controllers L1 ofthat respective machine. A first layer controller L1 may be referred toherein as a base layer controller. The machine controllers L2 and thebase layer controllers L1 can each perform specific functions incontrolling and monitoring the operation of the machine 16. Each machinecontroller L2 and each base layer controller L1 can be embodied as oneor more computer devices having a processor and memory, some of which iscomputer-readable tangible, non-transitory memory arranged on a printedcircuit board or otherwise available to the processor. Instructions maybe programmed into the memory of each of the machine controllers L2 andeach of the base layer controllers L1 and executed as needed via theprocessor of the respective controller L2, L1 to provide the controlfunctionality over the machines 16 and/or elements E within the controlof each respective machine controller L2 and/or each respective baselayer controller L1. The memory of each machine controller L2 and eachbase layer controller L1 can include, by way of example, sufficient readonly memory (ROM), optical memory, flash or other solid state memory,and the like. Transitory memory such as random access memory (RAM) andelectrically-erasable programmable read-only memory (EEPROM) may also beincluded, along with other required circuitry (not shown), including butnot limited to a high-speed clock,current/voltage/temperature/speed/position sensing circuitry,analog-to-digital (A/D) circuitry, digital-to-analog (D/A) circuitry, adigital signal processor, and any necessary input/output (I/O) devicesand other signal conditioning and/or buffer circuitry. Each machinecontroller L2 and each base layer controller L1 can include one or moremonitoring, measuring and/or control devices for monitoring, measuringand/or controlling the machines 16 and/or elements E within the controlof each respective machine controller L2 and/or each respective baselayer controller L1.

Each machine 16 includes a plurality of stations ST (shown in theexample of FIGS. 1 and 2 as stations ST1 . . . STn and referred toherein collectively as stations ST) for performing an operational cycleof the machine 16, where the operational cycle includes operations ofthe machine 16 performed in a predetermined sequence controlled by thebase layer controller L1 and/or the machine controller L2 of the machine16. The predetermined sequence in which the operations in theoperational cycle is performed can be defined by a sequence ofoperations 39 and/or a portion of a sequence of operations 39 definedfor that machine 16 by the machine controller L2 of the machine 16. Itwould be understood that the machine 16 would, in operation, repeatedlyperform the operational cycle comprising the sequence of operations 39under control of the machine controller L2 and/or the base layercontroller L1.

Each of the base layer controllers L1 (shown in the example of FIGS. 1and 2 as base layer controllers L1A . . . L1 z and referred to hereincollectively as the base layer controllers L1) controls operationsperformed by at least one of the stations ST in communication with therespective base layer controller L1. As shown in FIG. 2 , each stationST includes one or more elements E (shown in the example of FIG. 2 aselements E1 . . . Ep and referred to herein collectively as elements E),for performing various operations and/or tasks of the respective stationST. Using an illustrative example of a manufacturing and/or assemblyenterprise 12, examples of elements E used to perform the variousoperations of a manufacturing and/or assembly operation performed by amachine 16 and/or station ST can include clamps, cylinders, collets,pins, slides, pallets, etc., where the examples provided herein arenon-limiting.

Each station ST further includes one or more power sources P (shown inthe example of FIG. 2 as power sources P1 . . . Pr and referred toherein collectively as power sources P), for providing power to one ormore elements E and for selectively energizing a respective element E inresponse to a signal from the base layer controller L1. Each station STfurther includes one or more sensors S (shown in the example of FIG. 2as sensors S1 . . . Sq and referred to herein collectively as sensorsS), for sensing a state of at least one of the elements E and the powersource P of the station ST and providing an input to the base layercontroller L1 indicating the state sensed by the sensor S.

A state, which may be referred to as a condition state or as acondition, as used herein, refers to a state of the object, a condition,a status, a position, or other property being monitored, measured and/orsensed. Non-limiting examples of condition states including cycle starttime, cycle stop time, element start time, element travel, element stoptime, position of an element or object, a dimensional measurement of anobject which can include a dimensional measurement of a feature of anelement E, a feature of a machine 16, a feature of a workpiece (notshown) to which an operation is being performed by a machine 16 or anelement E, a condition of one or more of an element E, machine 16 orworkpiece, or a condition of the environment within the facility 14. Acondition state could further include for example, operating conditionssuch as on, off, open, closed, auto, manual, stalled, blocked, starved,traveling, stopped, faulted, OK, good, bad, in tolerance, out oftolerance, present, not present, extended, retracted, high, low, etc.,and can include for example, a measure of a physical property such aschemistry, temperature, color, shape, position, dimensional conditionssuch as size, surface finish, thread form, functional parameters such asvoltage, current, torque, pressure, force, etc., such that it would beunderstood that the terms state, condition and/or condition state asdescribing inputs to the AOS 10 are intended to be defined broadly. Byway of non-limiting example, a sensor S may be configured as a limitswitch, a proximity switch, a photo eye, a temperature sensor, apressure sensor, a flow switch, or any other type of sensor which may beconfigured to determine if one or more states are met during operationof the automated system 10, and to provide an output to the at least oneautomation controller, such as the base layer controller L1 and/or themachine layer controller L2, which is received by the controller L1, L2as an input corresponding to the state determined by the sensor S. Thesensor S output may be configured, for example, as a signal provided tothe base layer controller L1 and/or to the machine layer controller L2,and received by the base layer controller L1 and/or to the machine layercontroller L2 as an input including input data. The sensor S may beconfigured to provide a discrete or bit-form output. The sensor S may beconfigured as an analog sensor and may provide an analog output signalcorresponding to one or more of multiple states of a element E or agroup of elements E associated with the sensor S, or one or more ofmultiple states of an environment of the machine 16 and/or theenvironment of the facility 14 including the machine 16.

The predetermined sequence of operations in the operational cycle can bedefined by a sequence of operations 39 and/or a portion of a sequence ofoperations 39 defined for that machine 16 by the machine controller L2of the machine 16. In one example, the machine controller L2 can performthe functions of the machine controller L2 and the base layercontrollers L1, such that the machine 16 can be configured without thebase layer controllers L1. In this example, the machine 16 would, inoperation, repeatedly perform the operational cycle comprising thesequence of operations 39 under the independent control of the machinecontroller L2.

In another example, the controller functions may be divided between thebase layer controllers L1 and the machine controller L2, with the baselayer controllers L1 functioning as low level controllers and themachine controllers L2 functioning as a high level controllercoordinating the operation of the base layer controllers L1 within themachine 16. In this example, the machine 16 would, in operation,repeatedly perform the operational cycle comprising the sequence ofoperations 39 under the control of the machine controller L2 and thebase layer controllers L1, where the machine controller L2 acts as adata collector collecting the condition state data for each of theelements E of the machine 16 from each of the respective base layercontrollers L1, and acts as a local area controller to coordinate andcontrol the interaction of the base layer controllers L1 with eachother. In this example, each base layer controller L1 within the machine16 is in communication with each other base layer controller L1 withinthe machine 16 and with the machine controller L2 to communicatecondition states of each of the elements E controlled by that respectivebase layer controller L1, such that each base layer controller L1 canexecute control actions of the respective elements E under the controlof the respective base layer controller L1 in response to the conditionstate data received from the other base layer controllers L1 in themachine 16.

For illustrative purposes and by way of non-limiting example, theenterprise 12 shown in FIGS. 1 and 2 may be a production enterpriseincluding a plurality of manufacturing and/or assembly facilities 14,such as facilities 14A, 14B and 14C. In one example, the facilities 14A,14B and 14C may be co-located within the production enterprise 12, forexample, each of the facilities 14A, 14B and 14C may be sub-factories orassembly lines co-located in a larger building defining the productionenterprise 12. In another example, each of the facilities 14A, 14B and14C may be a stand-alone factory which may be geographically separatedfrom each other and in communication with each other and the enterpriseserver 12, for example, via the network 80. Facility 14A, forillustrative purposes, is shown in additional detail in FIGS. 1 and 2 ,and includes a facility server L3A which is in communication withmultiple systems SY such as systems SY1, SY2 and SY3 operating in thefacility 14A. In the example shown, system SY1 includes manufacturingand/or assembly operations consisting of multiple machines 16 such asmachines 16A, 16B, 16C, 16D and 16E.

In the illustrative example, machine 16A is shown in additional detailin FIG. 2 , consisting of multiple stations ST such as stations ST1through ST10. Machine 16A includes a machine controller L2A incommunication with multiple base layer controllers L1 such as base layercontrollers L1A, L1B and L1C. Each of the base layer controllers L1A,L1B and L1C acts to control multiple stations ST according toinstructions received from the machine controller L2A, to performoperations, for example, defined by a sequence of operations 39 storedin the machine controller L2A. For example, as shown in FIG. 2 , baselayer controller L1A can control the operations of stations ST1, ST2,ST3, ST4 by selectively activating the power sources P1, P2 and P3 toselectively actuate elements E1, E2, E3 and E4. The base layercontroller L1A receives sensor outputs from the sensors S1, S2, S3 andS4 which indicate condition states, for example, of the elements E1, E2,E3 and E4. The base layer controller L1A is in communication with baselayer controllers L1B and L1C in the present example, and receivescondition state input from base layer controllers L1B and L1C indicatingthe condition states of elements E5 through E10. The base layercontroller L1A selectively actuates the elements E1, E2, E3 and E4according to instructions stored in the memory of the base layercontroller L1A, inputs and instructions received from the machinecontroller L2A and in response to the condition states of the elementsE1 through E10, in the present example, received by the base layercontroller L1A. The examples described herein and shown in FIGS. 1 and 2related to machine 16A are illustrative and non-limiting. For example,each of the machines 16 controlled and/or managed by AOS 10 couldinclude a machine controller L2, however could differ in including abase layer controller L1 and/or the number of base layer controllers L1included in the machine 16, and could differ in the number, arrangement,function, etc. of the stations ST, elements E, sensors S and powersources P from the illustrative example of machine 16A shown in FIGS. 1and 2 .

In the present illustrative example, facility systems SY2 and SY3 shownin FIGS. 1 and 2 can operate in the facility 14A and can be operatedand/or managed using the AOS 10 in a manner and/or to provide outputswhich can affect the operations of system SY1 in facility 14A, includingaffecting the efficiency and/or downtime of the machines 16 included inthe system SY1. Each of the systems SY2, SY3 includes one or moreservers (not shown, referred to herein as a SY server) which can beembodied as one or more computer devices having a processor and memory,some of which is computer-readable tangible, non-transitory memoryarranged on a printed circuit board or otherwise available to theprocessor. Instructions may be programmed into the memory of each SYserver and executed as needed via the processor of the SY server toprovide monitoring and/or control functionality over the facilityoperations within the control of the respective SY system. The memory ofthe SY server can include, by way of example, sufficient read onlymemory (ROM), optical memory, flash or other solid state memory, and thelike. Transitory memory such as random access memory (RAM) andelectrically-erasable programmable read-only memory (EEPROM) may also beincluded, along with other required circuitry (not shown), including butnot limited to a high-speed clock,current/voltage/temperature/speed/position sensing circuitry,analog-to-digital (A/D) circuitry, digital-to-analog (D/A) circuitry, adigital signal processor, and any necessary input/output (I/O) devicesand other signal conditioning and/or buffer circuitry. Each of thesystems SY2, SY3 can include one or more monitoring, measuring and/orcontrol devices and/or sensors for monitoring, measuring and or sensinga state of the facility operations within the control of the respectiveSY system.

In the present illustrative example of a production enterprise 12,system SY2 can be a facility management system, which may be referred toherein as a facility infrastructure system SY2, for monitoring,measuring and/or controlling various factors of the infrastructure andoperating environment of facility 14A, such as electrical power supplyprovided to the various power sources P, water supply provided tohydraulic and/or coolant systems within the facility 14A and/or coolantsystems related to the machines 16, compressed air supply providedwithin the facility 14A, for example, to pneumatic systems of themachines 16, to pneumatically operated elements E, and/or topneumatically controlled manual tools such as pneumatic torch wrencheswhich may be used in manufacturing and/or assembly operations within thefacility 14A. It would be understood that variability in each of theelectrical power supply, water supply, and compressed air supply couldaffect the operation, efficiency and downtime of one or more of themachines 16 and/or elements E. For example, a decrease in the pressureof the compressed air supply provided to a pneumatically controlledelement E such as a cylinder may decrease the speed at which thecylinder element E travels, increasing the cycle time required for thecylinder element E to travel when performing an operation of a machine16. For example, an increase in temperature of cooling water circulatingin a cooling water jacket of a machine 16 such as a welding machine, maychange the efficiency of heat transfer from a work area of the machine16, affecting the tool life of the welding elements E in the machine 16and/or the cooling rate of the welds being formed in a product welded bythe machine 16. For example, variability in the voltage level of theincoming power supply provided to a power source P can affect theresponse time of a clamp element E activated by the power source P,thereby affecting the cycle time of the operation performed by the clampelement E. By way of example, system SY2 can monitor, measure, and/orcontrol ambient conditions within the facility 14A, or within a portionof the facility 14A, such as temperature, humidity, etc. For example,the facility 14A may be portioned into multiple zones, where at leastone of the machines 16 is located in each zone. By way of example, oneof the zones can include machines 16 which are performing operationssensitive to ambient temperature and/or humidity conditions, such as anelectronics fabrication operation or a painting operation, such thatvariability in the ambient temperature and/or humidity in that zone mayaffect the quality of the product produced by the machines 16 in thatarea. These examples are non-limiting and for illustrative purposes, andit would be understood that variability within facility controlledsystems and conditions such as power supply, water supply, compressedair supply, temperature, humidity, etc. can affect the operation of themachines 16, elements E and/or can affect the quality and/or conditionof the products produced by and/or the services provided by the machines16 in multiple ways too numerous to include herein. System SY2 cantransmit signals (inputs) to the facility server L3A indicatingcondition states of the various factors of the operating environment offacility 14A being monitored, measured, and/or controlled by thefacility server L3A.

In the present illustrative example of a production enterprise 12,system SY3 can include production control and product assuranceoperations and can monitor, measure and/or control various factors ofthe production control and product assurance operations which impact theoperation of manufacturing and production system SY1 of facility 14A.For example, the production control operations of system SY3 can monitorinventory levels (on order, in transit, in stock) of machine parts forthe machines 16, which may include replaceable service parts (motors,etc.) sensors S (limit switches, etc.) and/or elements E which caninclude durable (reusable) elements such as clamps, cylinders, etc.and/or consumable (replaceable) elements E such as drills, taps, clamppads, etc. required for a station ST to complete an operation and/or forthe machine 16 to operate. In another illustrative example, theproduction control operations of system SY3 can monitor inventory levels(on order, in transit, in stock) of vendor supplied (purchased)components and/or material which are provided to the machines 16, forexample, as raw material or work pieces on which operations areperformed by the machines 16, or are provided to the machines 16, forexample, as components to be assembled with other components to form afinished assembly. The product assurance operation, for example, canmonitor the condition of vendor supplier (purchased) components and/ormaterials and indicate the acceptance or rejection of the vendorsupplied materials, which could affect the availability of thatinventory to the machines 16. In another illustrative example, theproduct assurance operation can measure and output a condition state ofa component or raw material to the facility server L3 and/or to amachine controller L2 of a machine 16 processing the component or rawmaterial, such that the machine 16 in response can adjust settings basedon the measured condition state of the incoming component or rawmaterial. For example, a machine 16 may be an oven to temper componentsmade from raw material. The machine 16 via the facility controller L3can receive hardness data for the raw material from the productassurance system SY3 and adjust the tempering temperature of the ovenbased on the hardness of the raw material. These examples arenon-limiting and for illustrative purposes, and it would be understoodthat the condition of components and/or raw material monitored and/ormeasured by the product assurance operations of the system SY3, theinventory levels of components and/or raw material and the availabilityof machine parts for the machines 16 and elements E controlled andmonitored by the production control operations of the system SY3 canaffect the operational efficiency and/or downtime of the machines 16and/or elements E and/or can affect the quality and/or condition of theproducts produced by and/or the services provided by the machines 16 inmultiple ways too numerous to include herein. System SY3 can transmitsignals (inputs) to the facility server L3A indicating condition statesof the various factors of the operating environment of facility 14Abeing monitored, measured, and/or controlled by the facility server L3A.

In the present illustrative example, the facility server L3A acts as adata collector within the AOS 10 for collecting the inputs received fromthe systems SY1, SY2 and SY3, and can analyze and use the accumulateddata and inputs to identify and respond to operating conditionsthroughout the facility 14A, including implementing preventive actionsto minimize downtime, efficiency losses and/or productivity losses, bycontrolling and modifying the operations within the facility 16A, whichcan include outputting commands to the machine controllers L2A throughL2E and outputting commands to systems SY2 and SY3, for example, inresponse to condition states and inputs received from the machinecontrollers L2A through L2E and systems SY2 and SY3, to modify theoperating conditions within the facility 14A, the sequence of operations39 performed by the various stations ST, the machines 16 and/or stationsST used to perform one or more operations, etc., to improve efficiency,decrease and/or optimize power consumption within the facility, increaseproductivity, reduce or avoid downtime, etc. in response to the analysisof the data by the facility server L3A. The AOS 10 is advantaged byaccumulating the data and inputs from multiple production (SY1) andnon-production (SY2, SY3) systems and multiple machines within afacility 14, analyzing the accumulated data and inputs using a facilityserver L3 to identify issues which may not be identifiable by theindependent machine controllers L2, for example where such issues mayresult from interactions of multiple inputs which are outside the scopeof inputs controlled by any one of the machine controllers L2, and/orwhich may be identifiable only by combination of inputs from multiplesources (multiple machines 16, a machine 16 and system input from one ormore of systems SY2, SY3, etc.), and using the AOS 10 to identify,action responses to, manage and/or prevent issues using the collectiveresources of the facility 14.

In the present illustrative example, the enterprise server L4 acts as adata collector for the inputs and data received from the facilityservers L3A, L3B and L3C. The enterprise server L4 can analyze and usethe accumulated data and inputs to control and modify the operationswithin one or more of the facilities 16A, 16B, 16C, 16D and 16E,including implementing preventive actions to minimize downtime,efficiency losses and/or productivity losses, by controlling andmodifying the operations of one or more of the facilities 16A, 16B, 16C,16D and 16E, in response to an issue or condition identified in one ormore of the facilities 16A, 16B, 16C, 16D and 16E, which can include,for example, transferring production between facilities 16 inanticipation of or in response to a downtime event, to increaseefficiency based on the operational condition of a machine 16 in onefacility 14 as compared to an identical and/or substantially similarmachine 16 in another facility 14, to respond to inputs received fromthe non-production systems SY2 and/or SY3 indicating for example, afacility power supply issue or incoming material issue, etc. The AOS 10is advantaged by accumulating the data and inputs from facilities 14,analyzing the accumulated data and inputs using the enterprise server L4to identify issues which may not be identifiable by the independentfacility servers L3, for example where such issues may result frominteractions of multiple inputs which are outside the scope of inputscontrolled by or received into any one of the facility servers L3,and/or which may be identifiable only by a combination of inputs frommultiple facilities L4, and using the AOS 10 to identify, actionresponses to, manage and/or prevent issues using the collectiveresources of the enterprise 12.

The examples described herein and shown in FIGS. 1 and 2 related tofacility 14A are illustrative and non-limiting, and it would beunderstood that the facilities 14 other than facility 14A included inthe enterprise 12 can each include at least one machine 16 configuredsimilar to machine 16A to include a base layer controller L1 and amachine controller L2, however the number and configuration of each ofthe machines 16 may vary within a facility 14 and from one facility 14to another facility 14, and each of the machines 16 may include elementsE and sensors S arranged in stations ST other than those described forthe example of machine 16A to perform operations other than thoseperformed as described for machine 16A.

The example of an enterprise 12 including facilities 14 such asmanufacturing plants and/or assembly facilities is not intended to belimiting. An AOS 10 as described herein can be applied to the controland management of any type of enterprise 12 including machines 16performing coordinated operations, and as such it would be understoodthat the terms enterprise 12, facility 14, machine 16, element E andsensor S are intended to be defined broadly. By way of non-limitingexample, an enterprise 12 can be an amusement park including an AOS 10,where the facilities 14 and machines 16 are defined by different areasof the amusement park and the systems SY can include, for example, asecurity system for the amusement park and an infrastructure system(water, power, waste disposal, etc.) of the amusement park. In such anexample, an amusement ride facility 14A can include machines 16 formingthe amusement rides, an admission ticketing facility 14B can includemachines 16 for receiving and securing payment for tickets, a diningfacility 14C can include machines 16 for providing food service, aparking facility 14C can include machines 16 for receiving parking feesand monitoring and patrolling the parking area, etc. In anothernon-limiting example, an enterprise 12 including an AOS 10 may be aproperty development, such as an office building complex, where eachfacility 14 includes one or more buildings within the complex, and themachines 16 operating in each facility 14 include, for example,elevators, security cameras, heating and ventilation equipment, etc.

Referring now to FIGS. 3 and 4 , timing data collected from one or moreof the elements E, stations ST and/or machines 16 within the enterprise12 can be displayed as shown in FIG. 3 in a traditional sequence ofoperation (SOP) display format 33, and/or in a heartbeat display format35 shown in FIG. 4 . The SOP display format 33 may be referred to as aSOP timeline display or as a SOP display. In the SOP display 33 shown inFIG. 3 , the sequence of operations 39 corresponding to the data beingdisplayed is listed vertically (as shown on the page), and in thepresent example includes operations Op1 through Op9, with operation Op1being performed by elements E1 and E2 of a machine 16, operation Op 2being performed by elements E3 and E4, and so on. A baseline cycle,e.g., the design intent cycle, for each of the operations Op1 . . . Op9in the SOP 39 is graphically shown by a baseline cycle indicator 29. Theactual cycle for each of the operations Op1 . . . Op9 is graphicallyshown by an actual cycle indicator 31. Each of the actual cycleindicators 31 may be color coded, e.g., displayed in a color definingthe status of the cycle of that operation. In the example shown, theactual cycle indicators 31 are displayed in either a red or green color,with red indicating the actual cycle time is outside of a predeterminedtolerance for the cycle of that operation, and green indicating theactual cycle time is within tolerance.

In the heartbeat display 35 shown in FIG. 4 , the sequence of operations(SOP) 39 corresponding to the data is displayed on the horizontal axis(as shown on the page) with the actual cycle time of each operation Op1. . . Op9 shown in heartbeat display format by an actual cycle timeindicator 31, which may be color coded as previously described for FIG.3 , to indicate whether the cycle time for each respective operation iswithin tolerance. FIG. 4 further displays the heartbeat 88 of thesequence of operations 39, where the heartbeat 88 is determined, forexample, as described in U.S. Pat. No. 8,880,442 B2 issued Nov. 14, 2014to the inventor and incorporated by reference herein.

As shown in FIGS. 5 and 6 , the SOP display 33 and the heartbeat display35 can each be displayed on a graphical user interface 74 of a userdevice U and each can be embodied as a machine control interface (MCI)84 including one or more user interface elements (UIE) 86, also referredto herein as graphical control elements (GCE) or GCEs. The user device Ucan be one of a plurality of user devices U (shown in the example ofFIGS. 1 and 2 as user devices U . . . Uw and referred to hereincollectively as user devices U) connected to the network 80 and includedin the AOS 10 to receive data from the enterprise 12. In one example,the user device U can be a portable computing device such as a personalcomputer, notebook, tablet, smart phone, personal data assistant, etc.,including, as shown in FIG. 9 , a processor 76 and memory 78, some ofwhich is computer-readable tangible, non-transitory memory arranged on aprinted circuit board or otherwise available to the processor 76. Thememory 78 may include, by way of example, sufficient read only memory(ROM), optical memory, flash or other solid state memory, and the like.Transitory memory such as random access memory (RAM) andelectrically-erasable programmable read-only memory (EEPROM) may also beincluded, along with other required circuitry (not shown), including butnot limited to a high-speed clock, location sensing circuitry,analog-to-digital (A/D) circuitry, digital-to-analog (D/A) circuitry, adigital signal processor, and any necessary input/output (I/O) devicesand other signal conditioning and/or buffer circuitry. The user device Ucan include a connector port 72 for connecting the user device U to aperipheral device. In the example shown in FIG. 9 , the user device U isconnected to an enabling switch 50 such that the user device U isenabled as an automation human machine interface (HMI) device 175, alsoreferred to as an HMI control device.

The user device U includes a communications interface which can be awireless or wired interface, for connection of the user device U to thenetwork 80 for communication with one or more of the controllers L1, L2,the servers L3, L4, another of the user devices U, and/or the datastorage memory 90. In one example, the user may subscribe to receivealerts for one or more elements E and/or machines 16 being monitored bythe user, where the alerts may be received by the user on the userdevice U as one or more of a text message, instant message, e-mail, orother alert indicator. The user device U includes a graphical userinterface (GUI) 74, which in a preferred example is a graphical touchscreen or other touch-sensitive display, such that a user can providehaptic and/or tactile (touch) input to the user device 74, includingcommands, via the GUI 74 and/or standard tool bars 82. The GUI 74 canalso be referred to herein as a touch screen 74. A touch input can beprovided, by way of non-limiting example, by a touch action includinguser contact with touch screen 74, where user contact with the touchscreen is typically, but not necessarily, made by a portion of theuser's hand such as a finger or fingers, or portions thereof such as oneor more fingertips or knuckles, and/or by a surface of the hand such asthe side of the hand or heel of the palm. A touch action, by way ofnon-limiting example, can be a touch pressure, a touch motion, and/or acombination touch action including a touch pressure action and a touchmotion action. A touch pressure action, which may be referred to as atouch pressure, can refer to a point pressure applied to a localizedarea of the touch screen 74, and typically, but not necessarily, appliedby a fingertip or knuckle. A touch pressure can be characterized by apredetermined minimum pressure force which must be exerted on the touchscreen 74 to be recognized by the MCI 84 and/or the touch screen 74 asan intentional touch action, e.g., where sensing the minimum pressureforce differentiates the touch pressure from an incidental contact withthe touch screen 74. The touch pressure can be a “touch and hold” actioncharacterized by a point pressure which is sustained for a predeterminedminimum hold time such that the touch and hold action can be recognizedby the MCI 84 and/or the touch screen 74 as an intentional touch action,e.g., where sensing the minimum hold time differentiates the touchpressure from an incidental contact with the touch screen 74. The touchpressure can be a “touch and tap” action characterized by a pointpressure applied in a predetermined pattern or sequence of multipletouches, such as a double tap, triple tap, etc., where the sequence oftaps must be accomplished within a predetermined time interval such thatthe sequence of taps can be recognized by the MCI 84 and/or the touchscreen 74 as an intentional touch action, e.g., where sensing thesequence of taps occurring within the predetermined time intervaldifferentiates the touch pressure action from multiple incidentalcontacts with the touch screen 74. A touch motion can be characterizedby a pattern of continuous contact across a predetermined area or alonga predetermined path which must be exerted on the touch screen 74 by auser to be recognized by the MCI 84 and/or the touch screen 74 as touchaction. In one example, a touch motion may be a slide motion along apath defined by a UIE 86, where the MCI 84 may display an indicatorassociated with the UIE 86. In an illustrative example shown in FIG. 7 ,UIE 86C defines a slide path which is associated with the baseline cycleindicator 29 and the actual cycle indicator 31 of operation Op5displayed by the MCI 84. In the illustrative example, a touch motionalong the path defined by UIE 86C activates a command, when the userdevice U is enabled to control the machine 16 performing the SOP 39associated with the MCI 84, to actuate element E7 performing Op 5 to aposition in the cycle of Op 5. For example, a slide motion in thedirection of arrow 136C activates UIE86C to actuate element E7 tocondition, for example, a position, earlier in the cycle of operationOp5, as determined by the length or duration of the slide motion in thedirection of arrow 136C. For example, the length or duration of theslide motion in the direction of arrow 136C can be continued untilelement E7 is returned to the start condition of operation Op5, forexample, to a starting position for operation Op5. The example shown isnon-limiting, and it would be understood that touch motions includinglinear and/or non-linear patterns and/or paths may be used to define atouch action. By way of example, a touch motion may include a broadermotion, such as a swipe motion across the touch screen 74, to provide auser input to the MCI 84.

Data collected by AOS 10, including data collected from elements E,sensors S, machines 16, systems SY, etc. in the enterprise 12 can bedisplayed on the user device U using one or more machine controlinterfaces (MCI) 84, where each machine control interface 84 can begenerated by and/or stored in the memory of one or more of a machinecontroller L2, a facility server L3, the enterprise server L4 and/or thedata storage memory 90, and can be accessed, for example, by a userdevice U via the network 80, for downloading of the MCI 84 to the userdevice U such that a user can view data from the AOS 10 via the MCI 84and/or interface with the MCI 84 to monitor and/or control one or moremachines 16 as described herein. As shown in FIGS. 5-8 , an MCI 84 canbe embodied as one of the SOP display 33 of FIG. 3 and/or the heartbeatdisplay 35 of FIG. 4 . These examples are non-limiting, and it would beunderstood that the MCI 84 can include any arrangement of dataaccessible from the AOS 10 which can be displayed, and which may beenabled with one or more UIEs 86 to allow a user to interface with theMCI 84 to manipulate the data displayed on the touch screen 74 using oneor more of the UIEs 86 and/or the tool bars 82. For example, MCI 84 canbe a machine control interface for a specific station ST, a specificelement E, a specific machine M, a group of elements E, a group ofstations ST, a group of machines M and/or a zone 98 including multipleelements E, multiple stations ST and/or multiple machines M, a sequenceof operations (SOP) 39 or a portion thereof, a production line, afacility 14, etc. The UIEs 86 can be arranged relative to the MCI 84such that a user can intuitively interface with the MCI 84, for example,to activate the UIEs 86 to display additional information provided bythe AOS 10. By way of non-limiting example, one or more UIEs 86 can beconfigured such that a user touch input to the UIEs 86 can activate thedisplay of additional information in a pop-up window or another screen,can activate the display of a menu which may include additional UIEs 86for selecting information, display options and/or other MCIs 84, canactivate modification of the current display to show an alternate viewof the MCI 84 (for example, to toggle an MCI 84 between the SOP display33 shown in FIG. 5 and the heartbeat display 35 shown in FIG. 6 ) and/orcan activate modification of the current display to shown conditionstates (such as on, off, OK, out of tolerance, etc.) or statusindicators (such as stopped, blocked, starved, etc.) using one or moredifferentiating display features such as color coding, selectivelighting and/or highlighting of portions of the MCI 84, etc.

In an illustrative example described herein, the MCI 84 and/or the UIEs86 can be configured and/or enabled and an automation human machineinterface (HMI) device 175 (see FIGS. 9 and 12 ) such that the user, viaa touch input to the UIEs 86 of the MCI 84, can activate, manipulateand/or control a motion, action and/or operation of an element E,station ST, and/or machine 16 corresponding to the MCI 84 displayed onthe touch screen 74. One or more preconditions can be required prior toenabling the user device U and the MCI 84 displayed on the user device Ufor use as an automation HMI device 175, which can include, for example,one or more of restricting operation of the machine 16 corresponding tothe enabled MCI 84 to operating in manual mode, authenticating the useras an authorized user such as a qualified operator/programmer of themachine 16 corresponding to the enabled MCI 84, connecting an enablingswitch 50 to the user device U and activating the enabling switch 50 byuser contact with the enabling switch 50, etc. The automation HMI device175 can also be referred to as an HMI control device.

In the non-limiting example shown in FIG. 9 , the user device U caninclude at least one location device 80, such as a global positioningsystem (GPS) transmitter/receiver and/or a radio frequencyidentification (RFID) transmitter/receiver, for detecting the absolutelocation of the user device U and/or the location of the user device Urelative to, for example, another location or another location devicesuch as a location device 60 located on a machine 16 (see FIG. 10 ). Thelocation device 80 can be used to authenticate the user device U to theenterprise 12 or a portion thereof prior to allowing access by the userdevice U, for example, to AOS 10 and/or to the data storage memory 90and data stored therein. In one example, the location device 80 can beused to control geographic access to AOS 10 by the user device U byallowing access by the user device U to AOS 10 only when the user deviceU is located within a facility 14 and/or within a predetermined space,such as an enabled area 91 of a machine 16. The location device 80 canbe used to authenticate the user device U to another device including alocation device, such as an enabling switch 50 including a locationdevice 56 (see FIG. 9 ) and/or a machine 16 including a location device60 (see FIGS. 10 and 11 ).

As shown in FIGS. 5 and 6 , each of the SOP display 33 and the heartbeatdisplay 35 is shown as an MCI 84, which can be viewed by a user tomonitor the operations of the machine 16, stations ST and/or elements Eperforming the operations shown in the SOP 39. As shown in FIGS. 5 and 6, each of the SOP display 33 and the heartbeat display 35 MCIs 84 can beenabled with multiple UIEs 86 to allow a user to control and/ormanipulate functions of a machine 16 via the MCI 84 of the user deviceU, and such that the touch screen 74 provides both an output interfaceand an input interface between the user and the user device U. The UIEs86 respond to haptic and/or tactile (touch) contact from the user, andcan be configured such that a UIE 86 can be activated by touch pressureof a user, touch motion of a user such as a sliding motion, and/or acombination of these. In the illustrative example shown, each of theoperation steps Op1 through Op9 of the SOP 39 is enabled as a UIE 86,and each of the base cycle indicators 29 and/or actual cycle indicators31 are enabled as a UIE 86.

In addition to viewing and monitoring the conditions of a machine 16and/or an SOP 39 being performed by the machine 16, and as shown in anillustrative example in FIGS. 7 and 8 , a user can control operations ofa machine 16 via the touch screen 74 by manipulating one or more of theUIEs 86. One or more preconditions can be required to allow the user toaccess the MCI 84 for the machine 16 and/or to control operations of themachine 16 via an MCI displayed on the touch screen 74. In one exampledescribed in further detail herein, a precondition for using the userdevice U to control operations of a machine 16 can include connecting anenabling switch 50 to the user device, to provide an automation HMIdevice 175 which requires the user to occupy both hands in the use ofthe HMI control device 175, e.g., with one hand activating the enablingswitch 50 and the other hand manipulating the user device U and/or theMCI 84 displayed on the touch screen 74 of the user device U. In anotherexample, the user can be required to authenticate the user as anauthorized user qualified to access the MCI 84 to monitor and/or tocontrol operations of the machine 16, via a log in procedure and/orother authentication procedure which may be accomplished, for exampleusing the user device U. The authentication procedure may determine thelevel of access the user is provided via the user device U. For example,the user's access can be limited to accessing the MCI 84 for a machine16 only for viewing and/or monitoring data related to the machine 16including the operating condition of the machine 16, such that theuser's access does not allow the user to control and/or modifyoperations of the machine 16, as could be the case when the user isauthenticated to view data related to the machine 16 however is notqualified to control operations of the machine 16 and/or is otherwiserestricted from controlling operations of the machine 16. A user, viathe authentication process, can be given access to the MCI 84 and theUIEs 86 enabled to allow the user to control and/or modify operations ofthe machine 16, where, in an illustrative example, the user isauthenticated as a service person, engineer, machine programmer or otherperson qualified to control the machine 16.

The machine 16 can be configured, for example, via the machinecontroller L2 of the machine 16, such that the machine can be controlledvia the MCI 84 and the user device U only when the machine 16 is beingoperated in manual mode. As a precondition to control operations of themachine via the touch screen 74, the user device U may be required to bewithin a predetermined area of the machine 16. The predetermined areacan be referred to herein as a control enabled area 91 (see FIG. 10 ),which may vary in size and/or configuration (as shown in FIG. 11 forenabled areas 91C and 91D) for each machine 16. The control enabled area91 defines an area in which a user device U can be enabled to controloperations of a machine 16 in the enabled area 91. In one example, theenabled area may be enabled using a location device 60 installed on orin and/or otherwise located proximate to the machine 16, station ST,and/or element E being enabled for control via a user device U, wherethe location device 60 in communication with, for example, a locationdevice 80 on the user device U and/or a location device 56 on aperipheral device such as an enabling switch 50 connected to the userdevice U, defines the enabled area 91 in which the user device U cancontrol the respective machine 16, station ST, and/or element Eassociated with the respective location device 60. For example, as shownin FIG. 10 , a location device 60A can be configured to define anenabled area 91A for a machine 16A, the location device 60B can beconfigured to define an enabled area 91B for a machine 16B, and so on.

In one example, the location device 80 of the user device U incommunication with the location device 60 of the machine can prompt amachine controller L2 of a machine 16 to provide access to and/ordisplay an MCI 84 for that machine 16 or a menu including an option toselect the MCI 84 for that machine 16 when the user device U is within apredetermined distance of that machine 16, which can be defined by theenabled area 91 and/or can be defined by the location of the user deviceU, for example, in a facility and/or a portion of the facility includingthe machine 16. For example, referring to FIGS. 11 and 12 , FIG. 11shows a floor plan of a facility 14A including the location of varioususer devices U1 . . . U4 in the facility 14A at a given point in time.FIG. 12 shows an MCI 84 displaying a machine layout display 116 showingfor example, the floor plan of a facility 14A including machines 16A . .. 16F. In one example, the MCI 84 shown in FIG. 12 may be displayed toany user device U located in the facility 14A, and a user can access anMCI 84 for each of the machines 16A . . . 16G in the facility 14A bytouching and/or pressing a corresponding one of the UIEs 86G . . . 86Nof the MCI 84 shown in FIG. 12 . The MCI 84 for the selected machine 16A. . . 16G may be displayed, for example, as an SOP display 33 (see FIG.5 ) or a heartbeat display 35, or a menu may be displayed to the user onthe user device U to enable the user to select from multiple MCI 84display formats available for the selected machine 16.

In another example, where the user and/or the user device U isauthenticated or otherwise enabled for controlling one or more of themachines 16 via an MCI 84 displayed on the user device, the MCI 84 shownin FIG. 12 may indicate on the display those machines which are enabledfor control via the user device U. For example, referring to FIGS. 11and 12 , when a user device U2 is located in a control enabled area 91of a machine 16 for which control of that user machine 16 by user deviceU2 has been authorized, the machine icon on the display shown in FIG. 12may be differentiated on the display to indicate to the user that theuser device U2 is in a control enabled area 91 for that machine 16, andthe user can, from that location, control operations of that machine. Inan illustrative example, the user device U2 is shown in FIG. 11 as beinglocated within two overlapping enabled areas 91C and 91D definedrespectively for machines 16C and 16D. While the user device U2 islocated at this location, the icons representing the enabled areas 91C,91D are differentiated to indicate to the user of the user device U2that control of the machines 16C and 16D is enabled from that location.In the illustrative example, the icons for machines 16C and 16D aredifferentiated on the display in FIG. 12 by a double ring, however itwould be understood that any form of graphical differentiation could beused. For example, the control enabled areas 91C, 91D could bedifferentiated in the display by color, highlighting, etc.

Referring again to FIGS. 5 and 6 , each MCI 84 of the SOP display 33 andthe heartbeat display 35 can be enabled with multiple UIEs 86 to allow auser to the activate and/or manipulate the UIEs 86, and such that thetouch screen 74 provides both an output interface and an input interfacebetween the user and the user device U. Each of the UIE 86 can respondto haptic and/or tactile (touch) contact from the user, which may beapplied in a predetermined pattern to provide an input to the touchscreen 74. For example, an UIE 86 can be activated by a touch pressure(point pressure or press and hold) applied by, for example, a finger ofa user on the area of the touch screen 74 where the UIE 85 is located,by a touch motion of a user such as a sliding motion of the user'sfinger across the area of the touch screen 74 defining the UIE 86,and/or a combination of a touch pressure and a touch motion. In anillustrative example shown in FIG. 5 , the user can apply a touchpressure on a UIE 86, such as UIE 86D corresponding to operation Op8 inSOP 39, to activate the UIE 86D to display additional information aboutoperation Op8. In one example, applying a touch pressure on the UIE 86Dcan activate the user device U and/or the MCI 84 to display detailedinformation about the operation Op8, including listing the names anddetails of each of the elements E1, E2 performing the operation Op8,which can be displayed, by way of non-limiting example, in a pop-upwindow (not shown) imposed on the MCI 84 and/or in a new screen display.In another example, applying either of a touch pressure or a touchmotion such as a sliding motion to the UIE 86E corresponding to thebaseline cycle indicator 29 and/or the actual cycle indicator 31 of theoperation Op8 can activate the user device U and/or the MCI 84 todisplay additional information about the operation Op8, which mayinclude, for example, the baseline (design intent) start time, cycletime and stop time for the operation Op8, the actual start time, cycletime and stop time of operation Op8 in the operational cycle displayedin FIG. 5 , and any preconditions which may be required before operationOp8 is started. For example, completion of operation Op5 may be aprecondition to starting operation Op8 and such information may bedisplayed in response to the user activating the UIE 86E with a touchaction. The additional information can, by way of example, be displayedin a pop-up screen, in another screen, etc. FIG. 5 shows the actualcycle indicator 31 for operation Op8 is colored “RED”, and the remainingactual cycle indicators 31 for the other operations Op1 . . . Op7 andOp9 are colored “GREEN”, indicating, in the illustrative example, that afault alert or alarm has been set for operation Op8. By touching the UIE86E in a predetermined manner, the user can activate the user device Uand/or the MCI 84 to display additional information about the faultalert or alarm, such as the condition state generating the fault alertand/or one or more condition states of the machine 16 and/or theelements E1 . . . E7 which can be related to the fault alert. In anon-limiting example, the condition state generating the fault alertcould be one of the elements E1, E2 in one of a blocked, starved,stopped, etc. condition and/or could include input from one or moresensors S which are in communication with at least one of the elementsE1, E2 to determine a condition state of the elements E1, E2, where theinput from the sensors S is displayed to the user in response to theuser touching the UIE 86D in the predetermined manner. The additionalfault alert information can be displayed in a pop-up screen or anotherscreen, and/or the user device U can direct the user to another area ofthe AOS 10, for example, to an issue tracking system included in the AOS10, to view additional information such as causal information,corrective action status, and/or a countermeasure plan to assist inresolving the faulted condition. The examples provided herein areillustrative and non-limiting, and it would be understood that variousUIEs 86 can be defined by the MCI 84 which can be activated by a touchaction to display and/or provide additional information related to themachine 16 and/or SOP 39 being displayed on the touch screen 74. Forexample, a UIE 86 could be defined by the legend and actuable by a touchaction to display the criteria for designating an operation Op as “RED”or “GREEN.” It would be understood that UIEs 86 defined in the MCI 84shown in FIG. 6 could be similarly activated by a touch action toprovide a user with access to additional information related to theoperation Op and/or the cycle indicators 29, 31 associated with the UIE86.

FIGS. 7 and 8 show an illustrative example of controlling and/ormanipulating functions of a machine 16 via the MCI 84 of the user deviceU. In the example shown, each of the operation steps Op1 through Op9 ofthe SOP 39 is enabled as a UIE 86, and each of the base cycle indicators29 and/or actual cycle indicators 31 is enabled as a UIE 86. Asdescribed herein, one or more preconditions can be required to enablethe use of the MCI 84 and/or the user device U to control the machine16, which can include user authentication, locating the user device Uincluding the MCI 84 in an enabled area 91 defined by the machine 16associated with the MCI 84, connecting an enabling switch 50 to the userdevice U, activating the enabling switch 50 and/or restricting operationof the machine 16 to manual mode, e.g., disabling automated operatingmode while the MCI 84 and user device U are enabled to control themachine 16. In an illustrative non-limiting example shown in FIG. 7 ,where the MCI 84 and user device U has been enabled to control themachine 16, a user can control operation of the machine 16 associatedwith the MCI 84. In the example shown, a SOP 39 is performed by themachine 16 including operations Op1 . . . Op9. Non-limiting examples ofcontrol which can be executed using the enabled user device U and MCI 84are illustrated by the corresponding touch actions required to executethe control. For example, a touch action 136A applied to UIE 86A can beconfigured as a touch pressure such as a press and hold action, where auser pressing and holding pressure on UIE 86A will trigger, e.g.,actuate, performance of operation Op1 by machine 16, and specifically beelements E1, E2. Operation Op1, once initiated by the application of thetouch pressure, will continue to its conclusion so long as the usercontinues to hold pressure on the UIE 86A. If the touch action 136A isinterrupted prior to the conclusion of operation Op1, for example, bythe user removing the user's hand from touch screen 74, then operationOp1 ceases without concluding. The location of UIE 86A corresponds tothe display of “Op1 (E1,E2)” in the SOP 39 displayed by the MCI 84 ontouch screen 74, such that the location of UIE 86A and the command toactuate operation Op1 is intuitive to the user.

In another example, touch actions 136B and 136C, applied respectively toUIE 86B and UIE 86C, can be combination touch actions requiring a pressand slide motion, where a user applying pressure and sliding, forexample, a fingertip in a generally horizontal direction (as shown onthe page) along the timeline corresponding to the respective timelinesof operations Op1 and Op5, in the example shown, actuates the respectiveoperation Op1, Op5 corresponding to the activated UIE 86B, 86C. Thedirection and duration of the touch action 136B, 136C corresponds to theactuation of the operation. For example, operation Op1, once initiatedby applying the touch action 136B as a sliding pressure to UIE 86B inthe direction of the arrow representing touch action 136B, will continuefrom the start of operation Op1 to the conclusion of operation Op1 solong as the user continues to apply a sliding pressure on UIE 86B. Ifthe touch action 136B is interrupted prior to the conclusion ofoperation Op1, for example, by removing the user's hand from touchscreen 74, then operation Op1 ceases without concluding at theinterrupted point in the operational cycle of operation Op1.Continuation of operation Op1 from the interrupted point to theconclusion of operation Op1 can be reinitiated by reinitiating andapplying the sliding action 136B in the direction of the arrowindicating sliding action 136B. The location of UIE 86B corresponds tothe display of the base cycle indicator 29 and/or the actual cycleindicator 31 displayed by the MCI 84 on touch screen 74, such that thelocation of UIE 86B and the command to actuate operation Op1 isintuitive to the user. Similarly, use of a sliding pressure in ahorizontal direction along the timeline and/or cycle indicator 31 of theSOP display 33 as a form of touch action required to activate acorresponding UIE 86, such as UIE 86C for operation Op5, is intuitive tothe user.

Application of a touch action 136B in a direction opposing the directionshown by the arrow representing touch action 136B actuates the machine16 to return the event or motion to its starting position, e.g.,actuates elements E1, E2 in the present example to return to a startposition for operation Op1 and/or to a start condition defined byoperation Op1. If the touch action 136B in the opposing direction isinterrupted prior to the return of elements E1, E2 to the startposition, for example, by the user removing the user's hand from touchscreen 74, then operation Op1 ceases at the point of interruption of thetouch action 136B without returning the elements E1, E2 to the startposition and/or start condition of the operational cycle of operationOp1. It would be understood that a user could apply the touch action136B in a generally horizontal motion and/or in different directionsalong the timeline of operation Op1, with intermittent interruptions inthe touch action 136B, to evaluate the performance of operation Op1and/or for observation of the operation Op1 at various points in theoperation cycle of operation Op1 at and between the start and stop(finish) positions and/or conditions.

Similarly, as shown for operation Op 5 in the present example, applyinga touch action 136C as a sliding pressure to UIE 86C and in thedirection of the arrow representing touch action 136C, actuates themachine 16 to return the event or motion to its starting position, e.g.,actuates element E7 in the present example to return to a start positionfor operation Op5 and/or to a start condition defined by operation Op5.Element E7 will continue to return to the start position and/or startcondition of operation Op5 so long as the user continues to apply asliding pressure on UIE 86C in the direction of the arrow indicatingtouch action 136C. If the touch action 136C is interrupted prior to theconclusion of operation Op5, for example, by removing the user's handfrom touch screen 74, then operation Op5 ceases without concluding. Thelocation of UIE 86C corresponds to the display of the base cycleindicator 29 and/or the actual cycle indicator 31 displayed by the MCI84 on touch screen 74 for operation Op5, such that the location of UIE86C and the command to actuate operation Op5 is intuitive to the user.Application of a touch action 136C in a direction opposing the directionshown by the arrow representing touch action 136C, as discussed relatedto touch action 136B, actuates element E7 to continue from the start ofoperation Op1 to the conclusion of operation Op1 so long as the usercontinues to apply a sliding pressure on UIE 86B. It would be understoodthat a user could apply the touch action 136C in a generally horizontalmotion and/or in different directions along the timeline of operationOp5, with intermittent interruptions in the touch action 136C, toevaluate the performance of operation Op5 and/or for observation of theoperation Op5 at various points in the operation cycle of operation Op5at and between the start and stop (finish) positions and/or conditions.

Referring now to FIG. 8 , another example of a MCI 84 is shown, wherethe MCI 84 provides a heartbeat display 35 of the SOP 39 shown in FIG. 7. In the example shown, UIE 86F can be actuated as by a touch action136A, as described for FIG. 7 , to actuate operation Op1 by applying atouch action which in the example shown is a press and hold action.Operation Op1 will continue to conclusion so long as the user maintainsthe touch action 136A on the UIE 86F. Likewise, a user can apply touchactions 136D and 136E in a manner similar to that described for touchactions 136B and 136C of FIG. 7 . In the example shown in FIG. 8 , thetouch actions 136D and 136E, applied respectively to UIE 86G and UIE86H, can be combination touch actions requiring a press and slidemotion, where a user applying pressure and sliding, for example, afingertip in a generally vertical direction (as shown on the page) alongthe actual cycle indicator bar 31 (see FIG. 4 ) of the heartbeat display35 displayed by the MCI 84 which corresponds the respective operationsOp4 and Op5, in the example shown, actuate the respective operationsOp4, Op5 corresponding to the activates UIEs 86G, 86H. The direction andduration of the respective touch action 136D, 136E corresponds to theactuation of the respective operation Op4, Op5 in a vertical directioncorresponds with the performance direction of the touch action 136D,136E, and where, as described for FIG. 7 , an interruption in therespective touch action 136D, 136E interrupts performance of therespective operation Op4, Op5. For example, application of the slidingpressure touch action 136D to the cycle indicator bar 31 for operationOp4 in a direction shown by the arrow indicating the touch action 136D,e.g., in a vertical direction upward (as shown on the page) actuateselement E6 to progress toward conclusion of operation Op4. Likewise,application of the sliding pressure touch action 136E to the cycleindicator bar 31 for operation Op5 in a direction shown by the arrowindicating the touch action 136E, e.g., in a vertical direction downward(as shown on the page) actuates element E7 to progress toward the startof operation Op4. It would be understood that a user could apply thetouch actions 136D and 136E in a generally vertical motion and/or indifferent directions along the vertical bars (actual cycle indicators31) of the heartbeat display 35, with intermittent interruptions in thetouch action 136D, 136E, to evaluate the performance of thecorresponding operations Op4, Op5 and/or elements E6, E7, and/or forobservation of the operations Op4, Op5 and/or elements E6, E7 at variouspoints in the operation cycle of operations Op4, Op5 at and between thestart and stop (finish) positions and/or conditions. The location ofUIEs 86G and 86H corresponds to the display of the actual cycleindicator 31 in the heartbeat display 35 displayed by MCI 84 on touchscreen 74, such that the location of UIEs 86G and 86H and the commandsto actuate operations Op4 and Op5 are intuitive to the user. Similarly,use of a sliding pressure in a vertical direction along the cycleindicator bar 31 of the heartbeat display 35 as a form of touch actionrequired to activate a corresponding UIE 86, such as UIE 86G foroperation Op4, is intuitive to the user.

Still referring to FIGS. 7 and 8 , with the user device U enabled suchthat the MCI 84 can be used to control operations of a machine such asoperations Op1 . . . Op9 shown in SOP 39 displayed by MCI 84, it wouldbe understood that additional touch actions 136 (not shown) could beused as described for FIGS. 5 and 6 . The form of the touch action usedfor specific function, for example, the form of a touch action used toactivate a UIE 86 to display additional information related to anoperation, may be different when the user device U is enabled. Forexample, as previously described for FIG. 7 , applying a touch pressure136A to activate UIE 86A when the user device U is enabled as a HMIcontrol device (such that MCI 84 can be used by a user to controloperation Op1) actuates elements E1,E2 to perform the operation Op1.Applying the same touch pressure 136A to activate UIE 86A when the userdevice U is not enabled, as previously described for FIG. 5 , causes MCI84 to display additional information related to operation Op1.Accordingly, a different form of touch action can be used when the userdevice U is enabled to activate UIE 86A to display additionalinformation related to operation Op1. For example, a double tap touchaction could be used to activate UIE 86A to display additionalinformation related to operation Op1 when the user device U is enabledas an HMI control device. Other touch actions can be used to manipulateinformation displayed by the user device U. In one example, a user cantransition between MCI 84 shown in FIG. 7 and MCI 84 shown in FIG. 8 ,by applying a swipe action across the touch screen 74, such that theuser can alternate between the SOP display 33 and the heartbeat display35 of the SOP 39 when monitoring and/or controlling the machine 16performing the operations of SOP 39.

It would be understood that various combinations of touch actions 136,UIE 86 arrangements, and MCI 84 display configurations can be used toview, monitor and/or manipulate information displayed by an MCI 84 onthe user device U, including information accessible via AOS 10, and thatvarious combinations of touch actions 136, UIE 86 arrangements, and MCI84 display configurations can be used to control operations Op performedby a machine 16 via an MCI 84 using the user device U in an enabledstate, e.g., enabled as an HMI control device to control operations ofthe machine 16, and as such the examples provided herein are providedfor illustrative purpose and are non-limiting.

In one example, the response of the MCI 84 and/or the user device U to atouch action provided by a user to a UIE 86 can be determined by the MCI84 and/or the user device U using additional criteria which can include,for example, the authentication level of the user of the user device U.In one example, the user of the user device U can be authenticated, forexample, via a login system, as having “viewer only” access, such thatthe MCI 84 would be non-responsive to touch actions reserved forcontrolling the machine associated with the MCI 84, and would only beresponse to touch actions, for example, requesting viewing of additionalinformation. In this way, the MCI 84 may appear the same to a vieweronly user and to a user with control authorization, however the UIEs 86would be limited in response to the authority level of the user. Inanother example, the response of the MCI 84 and/or the user device U toa touch action provided by a user to a UIE 86 can be determined by theMCI 84 and/or the user device U using additional criteria which caninclude, for example, the location of the user device U, and/or thelocation of the user device in combination with the authenticatedauthority level of the user. For example, the control function responseto a touch action provided by a user to a UIE 84 may be deactivatedunless it is determined, for example, using the location device 80 ofthe user device U, that the user device U is located in an enabled area91 of the machine 16 associated with the MCI 84, as described related toFIGS. 10, 11 and 12 .

In another example, the response of the MCI 84 and/or the user device Uto a touch action provided by a user to a UIE 86 can be determined bythe MCI 84 and/or the user device U using additional criteria which caninclude, for example, detecting an enabling switch 50 connected to theuser device U, where the enabling switch 50 can be configured tointeract with the user device U and/or the MCI 84 such that both handsof the user are occupied with activating the enabling switch 50 andinterfacing with the user device U when controlling the machine 16 usingthe MCI 84. In one example, the enabling switch 50 must be manuallyactivated, e.g., the trigger 66 must be depressed by the user's hand, touse the UIEs 86 of the MCI 84 to control actions of the machine 16associated with the MCI 84. The criteria of a connected and/or activatedenabling switch 50 may be combined with at least one other criteria toenable the machine control functions of the UIEs 86. For example, thecontrol function response to a touch action provided by a user to a UIE84 may be deactivated unless it is determined, for example, that theuser device U is located in an enabled area 91 of the machine 16associated with the MCI 84, and the user of the user device U hasauthenticated authority to control the machine 16.

Referring now to FIGS. 9 and 12 , shown is a user device U connected toan enabling switch 50 such that the user device U can be enabled for useas an automation human machine interface (HMI) device 175 forcontrolling a machine 16, including controlling one or more of anelement E, station ST of the machine 16 and/or operation Op of a SOP 39performed by the machine 16. As a precondition for controlling themachine 16 via the user device U and/or enabling the user device U as anHMI control device 175, operation of the machine 16 in manual mode onlycan be required, such that control of the machine 16 via the enableduser device U, e.g., via the HMI control device 175, is limited tocontrol in a manual mode only. The enabling switch 50 may also be knownas a “dead man switch,” a “live man switch,” or an “operator presencecontrol (OPC)” as those terms are commonly understood related toautomation control. The enabling switch 50, as shown in FIG. 9 ,includes a switch connector 52 and switch cable 64 for connecting theenabling switch 50 to the user device U, for example, by connection ofthe switch connector 52 to a connector port 72 of the user device U. Inone example, the switch connector 52 and the connector port 72 can eachbe a Universal Serial Bus (USB) type connector, such that the enablingswitch 50 and the user device U can be in communication with each other.The length and/or configuration of the switch cable 64 can be of a typewhich requires a user to occupy both hands in the use of the HMI controldevice 175 when the enabling switch 50 is connected to the user deviceU. For example, the switch cable 64 should be limited in length and/ornon-extendable to prevent and/or avoid concurrent use of the enablingswitch 50 by one person and input to an MCI 84 displayed on the userdevice U by another person when the enabling switch 50 is connected tothe user device U. The illustrated example is non-limiting, and othermeans of limiting the concurrent triggering of the enabling switch 50and input to the touch screen 74 of the user device U by two differentusers could be used. For example, the enabling switch 50 may be mountedto the user device U by a bracket (not shown) configured to keep bothhands of a user occupied in the use of the HMI control device 175 whileretaining the enabling switch 50 in close proximity to the user device Uto prevent and/or avoid concurrent use of the enabling switch 50 by oneperson and touch input to the touch screen 74 by another person. In thisexample, the bracket may be selectively attachable to one or both of theenabling switch 50 and the user device U such that the enabling switch50 can be disconnected from the user device U when not required toenable the user device U as a HMI control device 175. The enablingswitch 50 can include a power source, which can be a replaceable and/orrechargeable power source such as a battery or power cell, and/or can bepowered by the power source of the user device U via the connectionestablished by the connector 52 and connector port 72.

The enabling switch 50 includes at least one trigger 66 for manuallytriggering, e.g., switching or activating, the enabling switch 50 to anenabled state. The trigger 66 can be a two-way switch designed to closewhen a grasping pressure is exerted on the trigger 66, for example, by ahand of a user, and to open when the grasping pressure is relieved,e.g., when the hand of the user relaxes and/or is removed from thetrigger 66. The trigger 66 can be a three-way switch designed to closewhen a grasping pressure is exerted on the trigger 66 to place thetrigger 66 in a mid-position, and to open when the grasping pressure ofa user is relieved from the trigger 66, and to open when the graspingpressure of a user is increased to fully compress, in the example shown,the trigger 66, such that the enabling switch 50 in a three-wayconfiguration requires the user to maintain a specific triggeringpressure on the trigger 66 to activate the enabling switch 50. Theenabling switch 50 can include a finger pad 68, which may be referred toas a grip pad or finger rest, for use in grasping the enabling switch 50and/or balancing the triggering pressure exerted by the user's hand onthe trigger 66. The enabling switch 50 can include a switch indicator 62to provide an output to the user indicating the condition status of theenabling switch 50. For example, the switch indicator 62 can beconfigured to change color to indicate connection to a user device U,location of the enabling switch U in an enabled area 91, switchcondition of the trigger 66 (open or closed), etc. In one example, theenabling switch 50 can include a locking mechanism including a removablekey 58 which must be installed to the enabling switch 50 to unlock theenabling switch 50 to an operable state. The locking mechanism and/orkey 58 can be of any suitable type, by way of example, including one ofa mechanical, magnetic, or electromagnetic key 58. In one example,access to the key 58 may be limited to authorized users, e.g., users whoare qualified to control a machine 16 using the HMI control device 175including the enabling switch 50.

The enabling switch 50 includes a processor 70 and a memory 54, some ofwhich is computer-readable tangible, non-transitory memory arranged on aprinted circuit board or otherwise available to the processor 70.Instructions embodying the methods described herein may be programmedinto memory 54 and executed as needed via the processor 70 to providefunctionality of the enabling switch 50 as described herein. The memory54 may include, by way of example, sufficient read only memory (ROM),optical memory, flash or other solid state memory, and the like.Transitory memory such as random access memory (RAM) andelectrically-erasable programmable read-only memory (EEPROM) may also beincluded, along with other required circuitry (not shown), including butnot limited to a high-speed clock, current/voltage/position sensingcircuitry, analog-to-digital (A/D) circuitry, digital-to-analog (D/A)circuitry, a digital signal processor, and any necessary input/output(I/O) devices and other signal conditioning and/or buffer circuitry. Theenabling switch 50 can include a location device 56 a location device,such as a GPS transmitter/receiver or an RFID which can be used toauthenticate location of the enabling switch 50 and/or to communicatewith another location device such as a machine location device 60 of amachine 16, a location device 80 of a user device U, etc., to establishthe location of the enabling switch 50 relative to the other locationdevice and/or within an area, such as the location of the enablingswitch 50 within a facility 14 and/or within an enabled area 91 of amachine 16.

In an illustrative example, at least three prerequisite conditions mustbe satisfied for a user device U to be enabled as an HMI control device175 using the enabling switch 50. In this example, the first conditionis connection of the enabling switch 50 to the user device U, forexample, by connection of the connector 52 to the connector port 72. Thesecond condition is providing an MCI 84 for the machine 16 to becontrolled by the HMI control device 175, e.g., by the enabled userdevice U, to the user device U for display on the touch screen 74 of theuser device U and enablement of the UIEs 86 required to control themachine 16 using touch input to the displayed MCI 84. A third conditionis activating the enabling switch 50 to an enabled state by activatingthe trigger 66 to close the switch of the enabling switch, as previouslydescribed, where the MCI 84 and/or the UIEs 86 defined by the MCI 84 areonly enabled for control of the machine 16 when the trigger 66 isactivated by the user to the enabled state.

In one example, an MCI 84 for controlling a specific machine 16 can bestored in the memory 54 of the enabling switch 50, such that theenabling switch 50 is customized, e.g., configured, for use with onlythat specific machine 16, and the MCI 84 is retrievable by the userdevice U from the MCI 84, for display by the user device U and controlof the specific machine 16, via the connection between the enablingswitch 50 and the user device U, e.g., via the connection established byconnector 52 and connector port 72. The enabling switch 50 can beprogrammed with, e.g., can receive and store the MCI 84 to memory 54,from AOS 10, for example, from a facility server L3 and/or viaconnection to the network 80. In another example, multiple MCIs 84corresponding to multiple machines 16 can be stored in the memory 54 ofthe enabling switch 50, such that the MCIs 84 corresponding to themachine 16 to be controlled by the HMI control device 175 can beselected from the multiple MCIs stored on the enabling switch 50 andretrieved by the user device U connected to the enabling switch 50, fordisplay on the touch screen 74 of the user device U. In another example,the MCI 84 can be retrieved from AOS 10 by the user device U, forexample, from a facility server L3 or data memory storage 90, forexample, via the network 80. In one example, connection of the enablingswitch 50 to the user device U can be required for the user device U toretrieve an MCI 84 from AOS 10 via the network 80. In one example, theenabling switch 50 can provide an authentication code or password to theuser device U for retrieving an MCI 84 from AOS 10 which may only beusable by the user device U while the enabling switch 50 is connected tothe user device U, as a means of authenticating the user device U to theAOS 10. In one example, the user of the user device U can be required toprovide a user password or user authentication code to the AOS 10 toaccess and retrieve the MCI 84 for download to the user device U, wherethe user password or authentication code can be used by the AOS 10 toauthenticate the user as an authorized user, e.g., a user who isqualified to control the machine 16 corresponding to the MCI 84 beingretrieved to the user device U.

In an illustrative example, one or more supplemental conditions may berequired in addition to the three prerequisite conditions, to enable theHMI control device 175 to control a machine 16 via a MCI 84 displayed bythe user device U. In one example of a supplemental condition, the HMIcontrol device 175 must be located within an enabled area 91 of themachine 16 to be controlled. Location of the HMI control device 175 inthe enabled area 91 can be established, for example, by communication ofthe location device 56 of the enabling switch 50 with the locationdevice 60 of the machine 16 to be controlled, for example, where each ofthe location devices 56, 60 can be RFID type devices. In anotherexample, each of the location devices 56, 60 can be GPS type devices,where the location of the HMI control device 175 relative to thelocation of the machine 16 can be established by GPS signals receivedfrom both location devices 56, 60 via the network 80, to a server orcontroller configured for that purpose, such as a facility server L3. Inthis example, and referring to FIGS. 11 and 12 , the HMI control device175C would satisfy the supplemental condition for control of machines16C and 16D by establishing the location in the enabled areas 91C and91D defined for the respective machines 16C and 16D using the locationdevices 60C, 60D and the location device 56 of the enabling switch 50C.As shown in FIG. 12 , a machine layout display 116 displayed to a useron the user device U2 can be differentiated (for example, by the doublerings differentiating areas 91C and 91D in FIG. 12 ) to indicate to theuser that machines 16C and 16D can be controlled by the user device U2based on the present location of the user device U2 in the overlappingarea of the enabled areas 91C and 91D.

In another example of a supplemental condition, the machine 16 to becontrolled must be placed in manual operating mode to enable control viaHMI control device 175. The placement of the machine 16 into manualoperating mode can be communicated by the machine controller L2 of themachine 16 being controlled, via the machine controller L2 incommunication with the facility server L3 and/or the network 80, suchthat the status of the machine 16 in manual operating mode can beconfirmed to and monitored by the MCI 84 via the user device U incommunication with machine controller L2 and/or the facility server L3via the network 80. The examples provided are non-limiting andillustrative, and other supplemental conditions could be required. Itwould be understood that if any one of the prerequisite conditions orany one of the supplement conditions, where supplemental conditions areapplied, are not met, the control functions of the MCI 84 would bedisabled however the user device U including the MCI 84 could be used toview and monitor data collected from and/or related to the operation ofthe machine 16 corresponding to the MCI 84, as previously described.

The detailed description and the drawings or figures are supportive anddescriptive of the present teachings, but the scope of the presentteachings is defined solely by the claims. While some of the best modesand other embodiments for carrying out the present teachings have beendescribed in detail, various alternative designs and embodiments existfor practicing the present teachings defined in the appended claims.

The invention claimed is:
 1. A system for controlling automation, thesystem comprising: a machine in communication with a network; whereinthe machine is configured to: repeatedly perform an operational cycleincluding a predetermined sequence of operations (SOP) defined for themachine; collect data generated by performance of at least one operationof the sequence of operations by the machine; and transmit the datagenerated by the performance of the at least one operation to thenetwork; wherein the machine can be selectively operated in an operatingmode which is one of an automated mode and a manual mode to perform theat least one operation; wherein the data generated by the performance ofthe at least one operation by the machine includes at least one of abaseline cycle time for performance of the at least one operation and anactual cycle time for performance of the at least one operation; thesystem further comprising: an automation controller in communicationwith the network; wherein the automation controller is configured tocontrol operation of the machine in the automated mode; a machinecontrol interface (MCI) corresponding to the machine; wherein themachine control interface (MCI) is configured to control operation ofthe machine in the manual mode; wherein the MCI is configured to beretrieved via the network by a user device including a touch interface,and to be displayed on the touch interface; wherein the machine controlinterface (MCI) displays, via a touch interface of the user device: thepredetermined sequence of operations (SOP) including the at least oneoperation; the data generated by performance of the at least oneoperation by the machine; a first touch activated user interface element(UIE) defined by the data displayed by the MCI; and at least one of: abaseline cycle indicator displaying the baseline cycle time of the atleast one operation; or an actual cycle indicator displaying the actualcycle time of the at least one operation; wherein the user deviceincluding the machine control interface (MCI) is enabled as anautomation human machine interface (HMI) device for controlling theoperation of the machine to perform the at least one operation in themanual mode; wherein a first touch action applied to the first touchactivated user interface element (UIE) controls performance of the atleast one operation by the machine; and wherein: the first UIE comprisesa path defined by the at least one of the baseline cycle indicator andthe actual cycle indicator; the first touch action applied to the firstUIE as a sliding pressure in a first direction along the path actuatesperformance of an operation cycle of the at least one operation to aconclusion of the operation cycle; the first touch action applied to thefirst UIE as a sliding pressure in a second direction along the path andopposing the first direction actuates performance of the operation cycleof the at least one operation to return to a start condition of theoperation cycle; and a selective interruption of the first touch actionalong the path interrupts performance of the operation cycle of the atleast one operation at a selected point in the operation cycle; whereinthe selected point in the operation cycle is between the start conditionand the conclusion of the operation cycle.
 2. The system of claim 1,wherein the MCI displays the at least one of the baseline cycleindicator and the actual cycle indicator in an SOP timeline display. 3.The system of claim 1, wherein the MCI displays the at least one of thebaseline cycle indicator and the actual cycle indicator in a heartbeatdisplay.
 4. The system of claim 1, further comprising: a second touchactivated user interface element (UIE) defined by the at least oneoperation displayed by the MCI; wherein a second touch action applied tothe second UIE controls performance of the at least one operation by themachine.